System and method for dynamic data management in a wireless network

ABSTRACT

A node is configured for transmitting a data packet over a wireless network. The node includes a controller configured to provide individualized control of a payload in the data packet. The controller is further configured to receive data to be transmitted over the wireless network, to determine a signal quality indicator for the wireless network, and to adjust the amount of the data included in the payload based on the signal quality indicator.

BACKGROUND

The present invention relates generally to communications in a wirelessnetwork and, more particularly, to the dynamic management of data in awireless local area network (WLAN).

In certain networked environments, such as medical facility networksinvolving patient monitoring over WLANs, it is desirable to leverage anexisting investment in a common network to deploy wireless bedside andtelemetry applications. However, as more and more wireless clientsaccess the WLAN, the network may become congested, with different typesof devices competing for priority on the WLAN. Such interference andincreased usage from multiple devices in wireless bands degrades overallnetwork performance and can lead to gaps in critical patient data anddropouts or delays in delivering alarms that can impact patient safety.For example, a patient-worn telemetry device set up to monitor ahigh-acuity patient for potentially life-threatening arrhythmia may betransmitting data on the WLAN, but may not be equipped with a localalarm to alert caregivers to a change in the patient's condition. It iscritical that the patient data and alarm messages from such a device berouted to, for example, a remote central monitoring station or portableelectronic device carried by a caregiver in real-time over the WLAN.There may also be multiple bedside monitors competing for access to theWLAN that, by contrast, may be equipped with local alarms to alertcaregivers to a change in conditions, such that any delay intransmission of an alarm on the network may not be as critical topatient safety. Furthermore, the respective acuity levels of the variouspatients being monitored by the various wireless monitoring devices onthe WLAN may be constantly changing, and the delay of data from alower-acuity patient being monitored by a patient-worn telemetry devicemay not be as critical to patient safety as a delay of data from ahigher-acuity patient. In the absence of effective means forprioritizing transmission of the patient data and alarm messages amongthese various devices, the more critical data may be delayed or lost.

The Institute of Electronic and Electrical Engineers (IEEE) 802.11standard for wireless LANs is a popular mechanism for setting upnetworks in many industrial, office, home and medical environments. Themain limitation of the legacy 802.11 is that it cannot support priorityclassifications to differentiate among different types of traffic. Thatis, every type of traffic is treated with equal fairness in the network.A newer standard called 802.11e has emerged which has prioritizedtraffic delivery for differentiating among traffic at different levelsof criticality. The 802.11e standard achieves this by having adifferentiated services control parameter in the IP layer forcontrolling wireless communication. For example, a six-bitDifferentiated Services Code Point (DCSP) may be assigned at the IPlayer and used in the MAC layer to classify and prioritize types oftraffic. Using the DSCP parameter for lower and higher priority trafficclasses, the higher priority traffic class is assigned shorter waittimes for transmission across the WLAN. However, even though 802.11e candifferentiate among traffic classes, under standard operatingconditions, the 802.11e DSCP parameter is static in nature, meaning thatit is not optimal under all monitoring scenarios. For example, when achange in the status or condition of a patient being monitored over amedical facility WLAN occurs, the 802.11e DSCP parameter does not adaptto those changing conditions. This makes the 802.11e DSCP defaultparameters unsuitable for some applications, such devices used forpatient monitoring in a medical facility, where dropouts and delays indelivering alarms can impact patient safety.

Furthermore, as noted above, there may be circumstances under which thesignal quality of the WLAN degrades, causing the connected data rate ofwireless clients accessing the WLAN to drop. When connected at the lowerdata rate, it takes longer for an individual wireless client to send itsdata and may result in lost data, delayed alarms or gaps in waveforms.Currently, wireless clients such as medical monitoring devices may oftenneed to transmit several different types of data, depending on theparticular monitoring scenario. However, in the absence of effectivemeans for the wireless client to manage the size of its data payload,the more critical data may be delayed or lost when interference andincreased usage from multiple devices in wireless bands degrades overallnetwork performance.

Accordingly, there is need for improved systems, devices and methods ofdata prioritization to increase the reliability of data transmissionover WLANs and to ensure robust transmission of critical data, such aspatient data in medical monitoring applications.

SUMMARY

The above-mentioned shortcomings, disadvantages and problems areaddressed herein which will be understood by reading and understandingthe following specification.

In an embodiment, a node is configured for transmitting a data packetover a wireless network. The node includes a controller configured toprovide individualized control of a payload in the data packet. Thecontroller is further configured to receive data to be transmitted overthe wireless network, to determine a signal quality indicator for thewireless network, and to adjust the amount of the data included in thepayload based on the signal quality indicator.

In another embodiment, a network includes an access point and nodesconfigured for wirelessly transmitting data packets over the network viathe access point. Each of the nodes includes a controller configured toprovide individualized control of a payload in each individual datapacket. The controller is further configured to receive data to betransmitted over the wireless network, to determine a signal qualityindicator for the wireless network, and to adjust the amount of the dataincluded in the payload based on the signal quality indicator.

In another embodiment, a method includes receiving data to betransmitted over a wireless network. The data is acquired by a nodeconfigured for wireless transmission of a data packet over the network.The node includes a controller configured to provide individualizedcontrol of a payload in the data packet. The method also includesdetermining a signal quality indicator for the wireless network, andadjusting the amount of the data included in the payload based on thesignal quality indicator.

Various other features, objects, and advantages of the invention will bemade apparent to those skilled in the art from the accompanying drawingsand detailed description thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of a network in accordance with anexemplary embodiment;

FIG. 2 is a block diagram illustrating an exemplary computer-implementedprocess for providing dynamic prioritization of data in the network;

FIG. 3 is a flow chart illustrating an exemplary method in accordancewith an embodiment;

FIG. 4 is a block diagram illustrating an exemplary computer-implementedprocess for providing dynamic management of payload data;

FIG. 5 is a flow chart illustrating an exemplary method in accordancewith an embodiment; and

FIG. 6 is a flow chart illustrating an exemplary method in accordancewith an embodiment.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings that form a part hereof, and in which is shown byway of illustration specific embodiments that may be practiced. Theseembodiments are described in sufficient detail to enable those skilledin the art to practice the embodiments, and it is to be understood thatother embodiments may be utilized and that logical, mechanical,electrical and other changes may be made without departing from thescope of the embodiments. The following detailed description is,therefore, not to be taken as limiting the scope of the invention.

Referring to FIG. 1, a schematically represented network 10 is shown.Wireless network 10 is generally configured to facilitate wirelesscommunication among two or more nodes 20, as well as other types ofdevices set up to access network 10. By way of example, network 10 maybe a WLAN, wherein various nodes 20 are configured to communicatewirelessly over network 10 according to IEEE 802.11e protocol via one ormore access points (APs) 14. Node 20 may be in a state of searching fordevices that belong to network 10 by periodically scanning actively bysending probe requests and scanning for probe response signalstransmitted by access point 14. Alternatively, node 20 may searchpassively by scanning for beacons transmitted by access point 14.According to an embodiment involving patient monitoring over a WLAN in amedical facility, network 10 may include one or more types of nodes 20(e.g., DASH or APEX PRO monitoring devices manufactured by GeneralElectric Company) monitoring patients of varying acuity levels. Thenodes 20 may be communicating patient data to a central monitoringstation 16 (e.g., a CIC PRO central monitoring station manufactured byGeneral Electric Company) over network 10 via one or more access points14 according to IEEE 802.11e protocol.

Node 20 is configured for access to a WLAN, such as network 10. In itsmost basic configuration, node 20 includes at least a processing unit 22and a memory 24. Depending on the exact configuration and type ofcomputing device, memory 24 may be volatile (such as RAM), non-volatile(such as ROM, flash memory, etc.) or some combination of the two.Processing unit 22 and memory 24 are included in, and form part of, acontroller 26.

Node 20 may also have additional features/functionality. For example,node 20 may also include additional storage (removable and/ornon-removable) including, but not limited to, magnetic or optical disksor tapes. Such additional storage is illustrated in FIG. 1 by aremovable storage 28 and a non-removable storage 30. Computer storagemedia includes volatile and nonvolatile, removable and non-removablemedia implemented in any method or technology for storage of informationsuch as computer readable instructions, data structures, program modulesor other data. Node 20 may also have one or more input devices 32 suchas keyboard, mouse, pen, voice input device, touch-input device, etc.One or more output devices 34 such as a display, speakers, printer, etc.may also be included. Node 20 may also be provided with a power source36, such as a battery pack or the like. Power source 36 provides powerfor computations and wireless data transmissions by node 20.

Node 20 may also include analog or digital signal inputs 38. Accordingto an embodiment wherein node 20 is a patient monitoring device, inputs38 may be a data acquisition component including, for example, signalacquisition hardware (e.g., signal amplifiers, galvanic isolationcomponents, analog-to-digital converters, etc.) and a softwareapplication executed by processing unit 22 to receive data from thesignal acquisition hardware and perform further processing. In thisembodiment, signal inputs 38 may be coupled to a patient by an array ofsensors or transducers 39, such as, for example, electrocardiogram (ECG)leads, invasive or noninvasive blood pressure devices, temperatureprobes, blood gas measurement probes, and airway gas sensors in order toreceive patient data.

Node 20 may also contain one or more communications connections 40 thatallow node 20 to communicate with other devices. Communicationsconnection 40 provides for communication with a WLAN via, for example,acoustic, RF, infrared and other wireless media. As discussed above, theterm computer readable media as used herein includes both storage mediaand communication media By way of example, communications connection 40may include a network interface card (NIC), such as a USB or SD wirelesscard for wirelessly communicating with different types of wirelessnetworks. The NIC includes a transceiver 42 that is coupled to anantenna 44 for transmitting and receiving data wirelessly over asuitable frequency channel. According to an embodiment, communicationsconnection 40 employs wireless configuration service over IEEE 802.11ewireless connections to ease network configuration, includinginfrastructure networks and ad hoc networks.

Communications connection 40 may also include hardware and/or softwareconfigured to evaluate the signal quality of network 10 between node 20and, for example, access point 14. By way of example, communicationsconnection 40 may be configured to measure a signal-to-noise ratio (SNR)for transmissions in the format of a power ratio between a signaltransmitted over network 10 and background noise. Similarly,communications connection 40 may be configured to measure a receivedsignal strength indicator (RSSI) indicative of the power present insignals transmitted over network 10. Communications connection 40 mayalso be configured to measure a noise floor value indicative of thelowest input signal power that can be recognized as a recoverableinformation signal by node 20. Communications connection 40 may also beconfigured to determine a retransmission rate indicative of a number oftransmission retries by node 20. Communications connection 40 may alsobe configured to determine a number of missed beacon signals from, forexample, AP 14. Other types of signal quality measurements areanticipated as well.

Referring still to FIG. 1, controller 26 includes an application 46 forprocessing payload data received by, acquired by or stored on node 20 inorder to assign a priority level to the data packets containing thepayload data. The term “payload data” as used herein generally refers tothe actual information to be communicated to an end user via a datapacket, such as, for example, patient parameter, alarm, waveform, devicetype, or location data, as opposed to header data that may be includedin a data packet. The term “data” as used herein generally refers todifferent types of payload data unless otherwise specified. The term“payload” as used herein generally refers to the portion of a datapacket containing payload data. According to an embodiment, application46 compares this data to defined thresholds to determine aclassification for the data and then performs a weighted sum calculationin order to determine the priority level. Controller 26 also includes anapplication 47 that assigns a differentiated services control parameterto data packets based on input from application 46. According to anembodiment, the differentiated services control parameter is aDifferentiated Services Control Point (DSCP) assigned at the IP layer todata packets received from application 46. The differentiated servicescontrol parameter as defined herein, however, may include priorityclassifiers other than DSCP applied at other layers as well. Controller26 also includes a network driver interface specification (NDIS)interface 48 that maintains the media access control (MAC) layer of datapackets received from application 47 and controls the operation of thecommunications connection 40. According to an embodiment, NDIS interface48 operates according to IEEE 802.11e protocol and uses thedifferentiated services control parameter to prioritize transmission ofdata packets via communications connection 40.

Referring now to FIG. 2, a block diagram illustrating acomputer-implemented process 50 for providing dynamic prioritization ofdata in network 10 is shown. In an embodiment, process 50 is directed toan adaptation of a differentiated services control parameter of an802.11e implementation of a WLAN. Specifically, process 50 asillustrated in FIG. 2 provides updates to the DSCP parameter in the IPlayer that determines the priority of data packets sent by node 20,where node 20 is a patient monitoring device transmitting data over anetwork 10 in a medical facility. An adaptive method for determining aDSCP for node 20 is desirable because the actual priority of datapackets transmitted onto network 10 by node 20 may vary over time. Ifnetwork 10 is congested, meaning that network 10 is busy with multipledevices attempting transmissions, a fixed DSCP value that is too low mayresult in dropouts and delays in delivering critical data from node 20that can impact patient safety. Similarly, a fixed DSCP value for node20 that is too high may lead to dropouts and delays in deliveringcritical data from other devices sending more critical data.Accordingly, depending on the criticality of data being transmitted bynode 20 at any given time, the appropriate DSCP value for efficient datatransmission can change over time.

While FIG. 2 is described and shown with respect to the adaptation of aDSCP value in an IP layer of a data packet, it is also envisioned thatother or additional parameters could be modified rather than the DSCPparameter. Additionally, it is further envisioned that process 50 couldbe applied to other wireless communication protocols beyond 802.11e,such as updated 802.11 protocols (e.g., 802.11n). Furthermore, whileFIG. 2 is described in the context of node 20 as a patient monitoringdevice transmitting patient data over a network 10 in a medicalfacility, it is envisioned that process 50 is applicable other types ofnodes and networked applications.

According to an embodiment of the invention, an adaptive DSCPdetermination on a per-node level is implemented as a distributed typeof control for a WLAN, the DSCP value defining a priority level forpacket transmission that is desired for wireless transmission for thatparticular node 20. The controller 26 in each node 20 is configured toperform a distributed and adaptive algorithm for adapting DSCP valuesthat works under the framework of the 802.11e standard for WLAN and useslocal computations to dynamically select DSCP values to satisfy thepriority requirements for that particular node 20. In the distributedcontrol scheme, the controller 26 in each of nodes 20 in network 10separately applies process 50 based on its individual operatingconditions. That is, based on a local determination of data priority,each node determines the appropriate adaptation of its DSCP value thatallows it to satisfy its own priority requirements.

Referring to FIG. 2, in process 50 at an individual node 20, controller26 receives data to be transmitted over network 10. The data may be, forexample, data acquired by node 20 or data previously stored on node 20.According to an embodiment wherein node 20 is a patient monitoringdevice transmitting patient data over network 10 in a medical facility,it is envisioned that the acquired data 60 may include, for example,parameter data 60 a, alarm data 60 b and waveform data 60 c. Parameterdata 60 a may include, for example, discrete (e.g., digital) values ofphysiologic vital sign data such as heart rate or electrocardiogram(ECG) data, blood pressure data (invasive or non-invasive), temperaturedata, blood gas measurement data (e.g., SpO2 data), and airway gasmeasurement data (e.g., CO2 data). Alarm data 60 b may include, forexample, data indicating that certain parameter data for a patient hasexceeded a predetermined limit and that assistance may be required(e.g., the patient has an excessive heart rate or temperature higherthan normal body temperature). Alarm data 60 b may also include dataindicating a change in the state of node 20 (e.g., sensor 39 has becomedisconnected or power source 36 is nearly discharged). Waveform data 60c may include, for example, analog or continuous patient physiologicaldata, such as an ECG waveform, sent at an appropriate data resolutionfor review by a caregiver. The data may also include, for example,device type data 60 d stored on node 20 regarding the type of patientmonitor (e.g., bedside monitor or telemetry device), and device locationdata 60 e that provides an indication of where node 20 is deployed inthe medical facility (e.g., intensive care unit, stepdown care unit,etc.). Other types of data may include, for example, electronic medicalrecord (EMR) data that may be important to monitoring the patient'scondition.

In the illustrated implementation of process 50 in FIG. 2, application46 processes the data 60 received by controller 26 for transmission overnetwork 10 and determines a priority level for the data. In particular,application 46 compares values of data 60 with a data threshold value 70in order to determine a data classification 80 for the data. Datathreshold values 70 for each type of data 60 may be established basedon, for example, critical levels or ranges into which values of data 60may fall. There may be a single data threshold value 70 for each type ofdata 60, or multiple data threshold values 70 establishing a range ofdata values for each type of data 60. According to an embodiment whereinnode 20 is a patient monitoring device transmitting patient data overnetwork 10 in a medical facility, it is envisioned that the datathreshold values may be established based on the relationship betweenvalues of data 60 and patient acuity. In the illustrated embodiment,values of parameter data 60 a are compared with appropriate datathreshold values 70 a. For example, data threshold values 70 a mayinclude user-defined limits or ranges for heart rate ECG data, bloodpressure data, temperature data, blood gas measurement data and airwaygas measurement data (e.g., CO2 data). Similarly, values of alarm data60 b are compared with appropriate data threshold values 70 b, andvalues of waveform data 60 c are compared with an appropriate datathreshold values 70 c.

Application 46 determines a data classification 80 for data 60 based onthe comparison with data threshold value 70. According to an embodimentwherein node 20 is a patient monitoring device transmitting patient dataover network 10 in a medical facility, it is envisioned that dataclassifications 80 are indicators of patient acuity based on thecomparison of data 60 with data threshold value 70. For example, if data60 includes values of heart rate parameter data 60 a that exceed a datathreshold value 70 a for heart rate data, then application 46 may assigna data classification 80 a indicating a high patient acuity level. Ifthe values of heart rate parameter data 60 a are below data thresholdvalue 70 a for heart rate data, then application 46 may assign a dataclassification 80 a indicating a lower patient acuity level. Similarly,application 46 may assign a data classification 80 b indicating a higheror lower acuity level depending on whether values of alarm data 60 bexceed a data threshold value 70 b for alarm data 60 b. Application 46may also assign a data classification 80 c indicating a higher or loweracuity level depending on whether values of waveform data 60 c exceed adata threshold value 70 c for waveform data 60 c. Data classifications80 d and 80 e may also be assigned respectively to device type data 60 dand device location data 60 e based on a comparison of this data withrespective data threshold values 70 d (e.g., node 20 is above or belowestablished size or portability constraints) and 70 e (e.g., node 20 isinside or outside of a particular distance range).

Application 46 determines a statistical weight value 90 for values ofdata 60 having an assigned data classification 80. Statistical weightvalues 90 are used to provide a structure under which varying levels ofdata priority may be adaptively determined by a weighted sumcalculation. According to an embodiment wherein node 20 is a patientmonitoring device transmitting patient data over network 10 in a medicalfacility, it is envisioned that corresponding statistical weight values90 are established for each of the various patient acuity-based dataclassifications 80 based on the priority to be accorded to each of thesedata classifications 80. By way of example, if data 60 includes valuesof heart rate parameter data 60 a to be transmitted that are assigned adata classification 80 a indicating a high patient acuity level, thenapplication 46 determines that a corresponding statistical weight value90 a is appropriate. In this particular circumstance, the determinedvalue of statistical weight value 90 a is higher than if the values ofheart rate parameter data 60 a to be transmitted are assigned a dataclassification 80 a indicating a lower patient acuity level. Statisticalweight values 90 b are established for the various alarm dataclassifications 80 b, and statistical weight values 90 c are establishedfor the various waveform data classifications 80 c. According to anembodiment, statistical weight values 90 b established for alarm dataclassifications 80 b may be higher than statistical weight values 90 cestablished for waveform data classifications 80 c, which in turn may behigher then statistical weight values 90 a established for parameterdata classifications 80 a. Similarly, statistical weight values 90 d and90 e are established for the various respective device type dataclassifications 80 d (e.g., lower weights may be established for nodes20 having device data classifications 80 d as bedside monitors withlocal alarms, while higher weights may be established for nodes 20having device data classifications 80 d as telemetry devices withoutlocal alarms) and location data classifications 80 e (e.g., higherweights may be assigned to nodes 20 having location data classifications80 e corresponding to an intensive care unit).

Application 46 also performs a weighted-sum calculation in order toassign an overall priority level 92 to data 60 to be transmitted by node20 over network 10. Various types of weighted sum calculation techniquesmay be employed, such as linear, non-linear and geometric weighted sumcalculations. The weighted sum calculation for priority level 92 factorsin each of the various statistical weight values 90 assigned to thevarious values of data 60 to be transmitted in a data packet overnetwork 10 and calculates an overall sum. In this way, data values 60corresponding to high patient acuity levels will increase the overallpriority level 92, and correspondingly increase the probability of thedata being transmitted over network 10. Data values 60 corresponding tolower acuity levels will decrease the overall priority level 92, andcorrespondingly decrease the probability of the data being transmittedover network 10 and increasing the probability of transmission of higherpriority data.

Application 47 receives overall priority level 92 from application 46,translates overall priority level 92 into a corresponding differentiatedservices control parameter value 94 (e.g., a six-bit DSCP valueaccording to IEEE 802.11e) and assigns differentiated services controlparameter value 94 to the IP layer of a data packet incorporating data60. NDIS interface 48 receives the differentiated services controlparameter value 94 and assigns the data packet to the corresponding dataqueue 96 at the MAC layer. The data packet incorporating data 60 is thensent to communications connection 40 for transmission to access point 14over network 10. The data packet incorporating data 60 may then beforwarded to, for example, central monitoring station 16 for display.

Referring now to FIG. 3, a flow chart illustrating a method 100 inaccordance with an embodiment is shown. Method 100 may be implemented inon, for example, the network shown in FIG. 1 and using, for example, theprocess described above with respect to FIG. 3. At a step 110, data tobe transmitted over a network is received. According to an embodiment,the data is acquired by a node 20 configured for wireless communicationwith an access point 14 according to a differentiated services controlparameter. The node 20 may be configured for wireless communication withthe access point 14 according to IEEE 802.11e protocol, and thedifferentiated services control parameter may a Differentiated ServicesCode Point. At a step 120, a priority level is assigned to the data. Thepriority level may be assigned by, for example, determining aclassification for the data performing a weighted sum calculation basedon the classification. At a step 130, the differentiated servicescontrol parameter may be adjusted based on the priority level.

In this way, the disclosed systems and methods provide dynamicadjustment of a wireless communications protocol based on data priorityin a wireless local area network. In medical monitoring applications,data is prioritized based on patient acuity, so that those patients atgreatest risk would have an increased probability of their data beingtransmitted over the network.

Referring now to FIG. 4, a block diagram illustrating an exemplarycomputer-implemented process 200 for providing dynamic management ofpayload data is shown. In an embodiment, process 200 is directed toadjusting the amount of data included in the payload of data packets an802.11e implementation of a WLAN. Specifically, process 200 asillustrated in FIG. 2 adjusts the amount of data included in datapackets sent by node 20, where node 20 is a patient monitoring devicetransmitting data over a network 10 in a medical facility. An adaptivemethod for adjusting the amount of data included in data packetstransmitted by node 20 is desirable because the signal quality oftransmissions over network 10 may degrade from time to time, causing theconnected data rate of nodes 20 accessing network 10 to drop. Whenconnected at the lower data rate, it takes longer for an individual nodeto send its data and may result in lost data, delayed alarms or gaps inwaveforms. Accordingly, depending on the signal quality of transmissionssent over network 10 at any given time, the appropriate amount of datain packets sent by node 20 for efficient data transmission can changeover time.

While FIG. 4 is described and shown with respect to the adaptation ofthe amount of data included in the payload of a data packet based onsignal quality in an 802.11 WLAN, it is also envisioned that process 200could be applied to other wireless communication protocols beyond802.11e, such as updated 802.11 protocols (e.g., 802.11n). Furthermore,while FIG. 4 is described in the context of node 20 as a patientmonitoring device transmitting patient data over a network 10 in amedical facility, it is envisioned that process 200 is applicable othertypes of nodes and networked applications.

According to an embodiment of the invention, an adaptive data packetpayload adjustment on a per-node level is implemented as a distributedtype of control for a WLAN. The controller 26 in each node 20 isconfigured to perform a distributed and adaptive algorithm for adjustingthe amount of data included in the payload of a data packet that worksunder the framework of the 802.11e standard for WLAN and uses localsignal quality measurements to dynamically adjust the payload of datapackets transmitted by a particular node 20. In the distributed controlscheme, the controller 26 in each of nodes 20 in network 10 separatelyapplies process 200 based on its individual operating conditions. Thatis, based on a local determination of signal quality, each node 20determines the appropriate adaptation of the payload of data packetsthat allows it to satisfy its own requirements.

Referring to FIG. 4, in process 200 at an individual node 20, controller26 receives data to be transmitted over network 10. As described abovewith respect to FIG. 2, the data may be, for example, data acquired bynode 20 or data previously stored on node 20. According to an embodimentwherein node 20 is a patient monitoring device transmitting patient dataover network 10 in a medical facility, it is envisioned that theacquired data 60 may include, for example, parameter data 60 a, alarmdata 60 b and waveform data 60 c. Parameter data 60 a may include, forexample, discrete (e.g., digital) values of physiologic vital sign datasuch as heart rate or electrocardiogram (ECG) data, blood pressure data(invasive or non-invasive), temperature data, blood gas measurement data(e.g., SpO2 data), and airway gas measurement data (e.g., CO2 data).Alarm data 60 b may include, for example, data indicating that certainparameter data for a patient has exceeded a predetermined limit and thatassistance may be required (e.g., the patient has an excessive heartrate or temperature higher than normal body temperature). Alarm data 60b may also include data indicating a change in the state of node 20(e.g., sensor 39 has become disconnected or power source 36 is nearlydischarged). Waveform data 60 e may include, for example, analog orcontinuous patient physiological data, such as an ECG waveform, sent atan appropriate data resolution for review by a caregiver. The data mayalso include, for example, device type data 60 d stored on node 20regarding the type of patient monitor (e.g., bedside monitor ortelemetry device), and device location data 60 e that provides anindication of where node 20 is deployed in the medical facility (e.g.,intensive care unit, stepdown care unit, etc.). Other types of data mayinclude, for example, electronic medical record (EMR) data that may beimportant to monitoring the patient's condition.

In the illustrated implementation of process 200 in FIG. 4, application46 also determines a signal quality indicator 210 for network 10. Inparticular, application 46 is configured to receive one or more signalquality measurements from communications connection 40, and to determinean overall signal quality indicator value. The signal qualitymeasurements may be, for example, an RSSI value, a noise floor value, anSNR value, a packet retransmission rate, and a missed beacon rate asdescribed above with reference to FIG. 1 and communications connection40. Signal quality indicator 210 may be based on a single signal qualitymeasurement (e.g., RSSI only), or may be derived from a combination ofsignal quality measurements received from communications connection 40(e.g., RSSI and SNR).

Application 46 adjusts the amount of the data 60 received by node 20that is included in the payload of a data packet based on signal qualityindicator 210. Specifically, if signal quality indicator 210 indicatesthat the measured signal quality available over network 10 is less thana certain threshold value or outside of a particular range, application46 may adjust the amount of data included in the payload of a datapacket. Based on the value of signal quality indicator 210, application46 may, for example, remove a subset of data 220 from the received data60 by eliminating certain types of the received data 60. In anembodiment wherein node 20 is a patient monitoring device transmittingpackets of patient data over network 10 in a medical facility, it isenvisioned that application 46 may remove a subset of data based onwhether such data is parameter data 60 a, alarm data 60 b, waveform data60 c, device type data 60 d or location data 60 e, leaving only certaintypes of data (e.g., alarms) to be included in the payload of a datapacket. According to another embodiment, based on the value of signalquality indicator 210, application 46 may, for example, remove a subsetof data 220 from the received data 60 by reducing the resolution of thereceived data 60. In an embodiment wherein node 20 is a patientmonitoring device transmitting packets of patient data over network 10in a medical facility, it is envisioned that application 46 may remove asubset of data by reducing the resolution of for example, parameter data60 a, alarm data 60 b, waveform data 60 c, device type data 60 d orlocation data 60 e. By way of example, if signal quality indicator 210that indicates that the measured signal quality available over network10 is less than a certain threshold value, application 46 may reduce theresolution of ECG waveform data from 120 Hz to 60 Hz. According toanother exemplary embodiment, if signal quality indicator 210 thatindicates that the measured signal quality available over network 10 isless than a certain threshold value, application 46 may reduce thenumber of data packet retransmission attempts. Application 46 includesthe remainder of the received data 60 as payload data 230 in a packetfor transmission onto network 10.

Referring now to FIG. 5, a flow chart illustrating a method 300 inaccordance with an embodiment is shown. Method 300 may be implementedon, for example, the network shown in FIG. 1 and using, for example, theprocess 200 described above with respect to FIG. 4. At a step 310, datato be transmitted over a network is received. According to anembodiment, the data is acquired by a node configured for wirelesstransmission of a data packet over network. The received data mayinclude, for example, physiologic data acquired by the patientmonitoring device, such as alarm data, waveform data, vital sign data,device type data, and location data. The node includes a controllerconfigured to provide individualized control of a payload in the datapacket. The node may be configured for wireless communication with theaccess point according to IEEE 802.11e protocol. At a step 320, a signalquality indicator is determined for the wireless network. The signalquality indicator may be based on, for example, an RSSI value, a noisefloor value, an SNR ratio value, a packet retransmission rate, and amissed beacon rate. At a step 330, the amount of the data included inthe payload is adjusted based on the signal quality indicator. Theamount of data included in the payload may be adjusted by, for example,removing a subset of data from the received data based on the type ofdata, such as alarm data, waveform data, vital sign data, device typedata, and location data. The amount of data included in the payload mayalso be adjusted by, for example, reducing the resolution of thereceived data.

In this way, the appropriate amount of the received data 60 included inpackets sent by node 20 is dynamically adjusted for efficient datatransmission depending on the signal quality of transmissions sent overnetwork 10 at any given time. As such, the disclosed systems and methodsincrease the likelihood that certain types of data are not delayed orlost when interference and increased usage from multiple devices inwireless bands degrades overall, network performance.

Referring now to FIG. 6, a flow chart illustrating an exemplary method400 in accordance with an embodiment is shown. In particular, FIG. 6illustrates an implementation of a method 400 combining the processesshown and described with respect to FIG. 2 and FIG. 4 such that dynamicdata management is performed based on both priority of the data to betransmitted over network 10 and the signal quality of transmissions sentover network 10 at any given time. Method 400 may be implemented in on,for example, the network shown in FIG. 1. At a step 410, data to betransmitted over a network is received. According to an embodiment, thedata is acquired by a node configured for wireless communication of adata packet over a network via, for example, an access point accordingto a differentiated services control parameter. The node may beconfigured for wireless communication with the access point according toIEEE 802.11e protocol, and the differentiated services control parametermay a Differentiated Services Code Point. The received data may include,for example, physiologic data acquired by the patient monitoring device,such as alarm data, waveform data, vital sign data, device type data,and location data. At a step 420, a priority level is assigned to thedata. The priority level may be assigned by, for example, determining aclassification for the data performing a weighted sum calculation basedon the classification. At a step 430, the differentiated servicescontrol parameter may be adjusted based on the priority level. At a step440, a signal quality indicator is determined for the network. Thesignal quality indicator may be based on, for example, an RSSI value, anoise floor value, an SNR ratio value, a packet retransmission rate, anda missed beacon rate. At a step 450, the amount of the data included inthe payload is adjusted based on the signal quality indicator. Theamount of data included in the payload may be adjusted by, for example,removing a subset of data from the received data based on the type ofdata, such as alarm data, waveform data, vital sign data, device typedata, and location data. The amount of data included in the payload mayalso be adjusted by, for example, reducing the resolution of thereceived data.

While the invention has been described with reference to preferredembodiments, those skilled in the art will appreciate that certainsubstitutions, alterations and omissions may be made to the embodimentswithout departing from the spirit of the invention. Accordingly, theforegoing description is meant to be exemplary only, and should notlimit the scope of the invention as set forth in the following claims.

1. A node configured for transmitting a data packet over a wirelessnetwork, the node comprising: a controller configured to provideindividualized control of a payload in the data packet, the controllerfurther configured to receive data to be transmitted over the wirelessnetwork; determine a signal quality indicator for the wireless network;and adjust the amount of the data included in the payload based on thesignal quality indicator.
 2. The node of claim 1, wherein the signalquality indicator is based on one of a received signal strengthindicator value, a noise floor value, a signal-to-noise ratio value, apacket retransmission rate, and a missed beacon rate.
 3. The node ofclaim 1, wherein the controller is configured to adjust the amount ofdata included in the payload by removing a subset of data from thereceived data.
 4. The node of claim 3, wherein the node is a patientmonitoring device, and wherein the received data includes physiologicdata acquired by the patient monitoring device.
 5. The node of claim 4,wherein the subset of data includes one of alarm data, waveform data,and vital sign data.
 6. The node of claim 1, wherein the controller isconfigured to adjust the amount of data included in the payload byreducing the resolution of the received data.
 7. The node of claim 1,wherein the node is configured for wireless communication with theaccess point according to IEEE 802.11e protocol.
 8. A networkcomprising: an access point; and nodes configured for wirelesslytransmitting data packets over the network via the access point; whereineach of the nodes includes a controller configured to provideindividualized control of a payload in each individual data packet, thecontroller further configured to receive data to be transmitted over thewireless network; determine a signal quality indicator for the wirelessnetwork; and adjust the amount of the data included in the payload basedon the signal quality indicator.
 9. The network of claim 8, wherein thesignal quality indicator is based on one of a received signal strengthindicator value, a noise floor value, a signal-to-noise ratio value, apacket retransmission rate, and a missed beacon rate.
 10. The network ofclaim 8, wherein the controller is configured to adjust the amount ofdata included in the payload by removing a subset of data from thereceived data.
 11. The network of claim 10, wherein each of the nodes isa patient monitoring device, and wherein the received data includesphysiologic data acquired by the patient monitoring device.
 12. Thenetwork of claim 11, wherein the subset of data includes one of alarmdata, waveform data, and vital sign data.
 13. The network of claim 8,wherein the controller is configured to adjust the amount of dataincluded in the payload by reducing the resolution of the received data.14. The network of claim 8, wherein the node is configured for wirelesscommunication with the access point according to IEEE 802.11e protocol.15. A method comprising: receiving data to be transmitted over awireless network, wherein the data is acquired by a node configured forwireless transmission of a data packet over the network, the nodeincluding a controller configured to provide individualized control of apayload in the data packet; determining a signal quality indicator forthe wireless network; and adjusting the amount of the data included inthe payload based on the signal quality indicator.
 16. The method ofclaim 15, wherein the determining the signal quality indicator includesdetermining the indicator based on one of a received signal strengthindicator value, a noise floor value, a signal-to-noise ratio value, apacket retransmission rate, and a missed beacon rate.
 17. The method ofclaim 15, wherein adjusting the amount of data included in the payloadincludes removing a subset of data from the received data.
 18. Themethod of claim 17, wherein the node is a patient monitoring device,wherein receiving the data includes receiving physiologic data acquiredby the patient monitoring device, and wherein the subset of dataincludes one of alarm data, waveform data, and vital sign data.
 19. Themethod of claim 17, wherein the controller is configured to adjust theamount of data included in the payload by reducing the resolution of thereceived data.
 20. The method of claim 15, wherein the node isconfigured for wireless communication with the access point according toIEEE 802.11e protocol.